Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silence extra output on rpmspeq query on Buildsystem specs #3414

Merged
merged 1 commit into from
Oct 30, 2024

Conversation

pmatilai
Copy link
Member

Dynamic spec parsing emits "Reading " messages to make it clear something out of the ordinary is going on, but this is undesireable on rpmspeq queries. Luckily there's a trivial solution: rpmbuild where you want these messages runs in verbose mode by default whereas rpmspec does not. So just moving the message to INFO level does exactly the right thing in both the above cases and as an added bonus, rpmbuild --quiet too. Add a test to go.

Fies: #3413

@pmatilai pmatilai requested a review from a team as a code owner October 30, 2024 07:15
@pmatilai pmatilai requested review from dmnks and removed request for a team October 30, 2024 07:15
Copy link
Contributor

@dmnks dmnks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two nitpicks for the commit message:

  • rpmspeq would be a funny contraction of rpmspec -q but probably just a typo 😄
  • rpmbuild --quiet doesn't seem to be affected by this, it sets the log level up to RPMLOG_WARNING whereas RPMLOG_NOTICE is higher

@pmatilai
Copy link
Member Author

Heh, funny typo indeed 😄
And right, I didn't actually try rpmbuild --quiet with this, would've been obvious it already works the way it should. Will fix, just a sec.

@dmnks
Copy link
Contributor

dmnks commented Oct 30, 2024

Sorry to be that guy... but the commit summary still says rpmspeq 😆
(The point is to allow for grepping for "rpmspec" in commit logs which sometimes comes in handy.)

Dynamic spec parsing emits "Reading <path>" messages to make it clear
something out of the ordinary is going on, but this is undesireable
on rpmspec queries. Luckily there's a trivial solution: rpmbuild where
you want these messages runs in verbose mode by default whereas rpmspec
does not. So just moving the message to INFO level does exactly the
right thing in both the above cases. Add a test to go.

Fies: rpm-software-management#3413
@pmatilai
Copy link
Member Author

Argh, I didn't even realize there was a second instance 😆

@pmatilai
Copy link
Member Author

And don't apologize for spotting typos, there's nothing worse than a typo in a commit message because you can't fix it afterwards and yep, it often makes finding the thing you're looking for much more difficult.

@dmnks dmnks merged commit bf2c1c3 into rpm-software-management:master Oct 30, 2024
1 check passed
@pmatilai
Copy link
Member Author

Argh, it really was not my morning:
Fies: #3413

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants